Tue Nov 24 2020 09:57:58 GMT+1100 (Australian Eastern Daylight Time)

Metadata

Test Environment: TEST
Browser: Chrome 81.0.4044.138
Platform: Windows 10
Parallel: Scenarios
Executed: Remote

Feature:Login to the FT1.9 application as various user 1

As a user
I should be able to open the Homepage of the Application
and should be able to login using valid credentials only

@test
Scenario:Browse the Ft1.9 application and validate
4

Given User navigates to the Home page of FT1.9 application 1s 162ms

When User navigates 'Home' and verifies 'WELCOME TO MYFASTTRACK' 4ms

Then user should be able to validate 'WELCOME TO MYFASTTRACK' 8ms

After 477ms Screenshot +

After 25ms Show Error + 
                                            
 NoSuchElementError: No element found using locator: by.cssContainingText("span.mat-button-wrapper", " Log Out ")
    at C:\Users\psingh\Desktop\Priti\Automation1.9\TestAutomationFramework-FT1.9\node_modules\protractor\built\element.js:814:27
    at ManagedPromise.invokeCallback_ (C:\Users\psingh\Desktop\Priti\Automation1.9\TestAutomationFramework-FT1.9\node_modules\selenium-webdriver\lib\promise.js:1376:14)
    at TaskQueue.execute_ (C:\Users\psingh\Desktop\Priti\Automation1.9\TestAutomationFramework-FT1.9\node_modules\selenium-webdriver\lib\promise.js:3084:14)
    at TaskQueue.executeNext_ (C:\Users\psingh\Desktop\Priti\Automation1.9\TestAutomationFramework-FT1.9\node_modules\selenium-webdriver\lib\promise.js:3067:27)
    at C:\Users\psingh\Desktop\Priti\Automation1.9\TestAutomationFramework-FT1.9\node_modules\selenium-webdriver\lib\promise.js:2927:27
    at C:\Users\psingh\Desktop\Priti\Automation1.9\TestAutomationFramework-FT1.9\node_modules\selenium-webdriver\lib\promise.js:668:7
    at processTicksAndRejections (internal/process/task_queues.js:97:5)Error
    at ElementArrayFinder.applyAction_ (C:\Users\psingh\Desktop\Priti\Automation1.9\TestAutomationFramework-FT1.9\node_modules\protractor\built\element.js:459:27)
    at ElementArrayFinder.(computed) [as click] (C:\Users\psingh\Desktop\Priti\Automation1.9\TestAutomationFramework-FT1.9\node_modules\protractor\built\element.js:91:29)
    at ElementFinder.(computed) [as click] (C:\Users\psingh\Desktop\Priti\Automation1.9\TestAutomationFramework-FT1.9\node_modules\protractor\built\element.js:831:22)
    at C:\Users\psingh\Desktop\Priti\Automation1.9\TestAutomationFramework-FT1.9\stepdefinitions\hooks.ts:16:21
    at Generator.next ((anonymous))
    at C:\Users\psingh\Desktop\Priti\Automation1.9\TestAutomationFramework-FT1.9\JSFiles\stepDefinitions\hooks.js:8:71
    at new Promise ((anonymous))
    at __awaiter (C:\Users\psingh\Desktop\Priti\Automation1.9\TestAutomationFramework-FT1.9\JSFiles\stepDefinitions\hooks.js:4:12)
    at World.(anonymous) (C:\Users\psingh\Desktop\Priti\Automation1.9\TestAutomationFramework-FT1.9\stepdefinitions\hooks.ts:15:45)

Feature:FT2-599-Account Management 1 1

@test
Scenario:QA-69 Verify if the participant is able to update his bank details
3 1 1

Given A participant "William Mcmahon" logged in to FastTrack application 10s 600ms

And user navigates to 'Account' -> 'Finance' tab and clicks 'Bank details' tab 1s 944ms

When user is able to view,add,update the bank details 1s 197ms Show Error + 
                                            
 TimeoutError: Wait timed out after 43ms
    at C:\Users\psingh\Desktop\Priti\Automation1.9\TestAutomationFramework-FT1.9\node_modules\selenium-webdriver\lib\promise.js:2201:17
    at ManagedPromise.invokeCallback_ (C:\Users\psingh\Desktop\Priti\Automation1.9\TestAutomationFramework-FT1.9\node_modules\selenium-webdriver\lib\promise.js:1376:14)
    at TaskQueue.execute_ (C:\Users\psingh\Desktop\Priti\Automation1.9\TestAutomationFramework-FT1.9\node_modules\selenium-webdriver\lib\promise.js:3084:14)
    at TaskQueue.executeNext_ (C:\Users\psingh\Desktop\Priti\Automation1.9\TestAutomationFramework-FT1.9\node_modules\selenium-webdriver\lib\promise.js:3067:27)
    at C:\Users\psingh\Desktop\Priti\Automation1.9\TestAutomationFramework-FT1.9\node_modules\selenium-webdriver\lib\promise.js:2927:27
    at C:\Users\psingh\Desktop\Priti\Automation1.9\TestAutomationFramework-FT1.9\node_modules\selenium-webdriver\lib\promise.js:668:7
    at processTicksAndRejections (internal/process/task_queues.js:97:5)
From: Task: (anonymous wait)
    at scheduleWait (C:\Users\psingh\Desktop\Priti\Automation1.9\TestAutomationFramework-FT1.9\node_modules\selenium-webdriver\lib\promise.js:2188:20)
    at ControlFlow.wait (C:\Users\psingh\Desktop\Priti\Automation1.9\TestAutomationFramework-FT1.9\node_modules\selenium-webdriver\lib\promise.js:2517:12)
    at Driver.wait (C:\Users\psingh\Desktop\Priti\Automation1.9\TestAutomationFramework-FT1.9\node_modules\selenium-webdriver\lib\webdriver.js:934:29)
    at run (C:\Users\psingh\Desktop\Priti\Automation1.9\TestAutomationFramework-FT1.9\node_modules\protractor\built\browser.js:58:33)
    at ProtractorBrowser.to.(computed) [as wait] (C:\Users\psingh\Desktop\Priti\Automation1.9\TestAutomationFramework-FT1.9\node_modules\protractor\built\browser.js:66:16)
    at C:\Users\psingh\Desktop\Priti\Automation1.9\TestAutomationFramework-FT1.9\stepdefinitions\When.ts:302:17
    at Generator.next ((anonymous))
    at fulfilled (C:\Users\psingh\Desktop\Priti\Automation1.9\TestAutomationFramework-FT1.9\JSFiles\stepDefinitions\When.js:5:58)

And user is able to land on ' Bank Details ' Page 0s

After 424ms Screenshot +

@test
Scenario:Verify Registration status of the participant 44472
5

Given A participant "William Mcmahon" logged in to FastTrack application 10s 396ms

And user navigates to 'Account' -> 'Setting' tab and clicks 'Registration Status' tab 6s 250ms

When user views the 'Registration status' details 1s 8ms

Then user should be able to see the 'Registration status' details 4ms

After 808ms Screenshot +

Feature:User virifies the the Calender page 8

@test
Scenario:Verify that user can view the 'Calendar' page
5

Given A participant "William Mcmahon" logged in to FastTrack application 10s 539ms

And user navigates to 'Calendar' -> 'Nothing' tab and clicks 'Nothing' tab 6s 345ms

When user views the 'Calendar' details 1s 3ms

Then user is able to land on 'Calendar' Page 8s 4ms

After 457ms Screenshot +

@test
Scenario:Verify that user can view the 'Calendar' page
5

Given A participant "William Mcmahon" logged in to FastTrack application 10s 255ms

And user navigates to 'Calendar' -> 'Filter' tab and clicks 'Nothing' tab 6s 295ms

When user views the 'Calendar' page with 'filter' 1s 8ms

Then User verifies the list of filters on 'Calendar' page and its detail 12s 4ms

After 452ms Screenshot +

@test
Scenario:Verify that user can view the 'Metro' details on 'Calendar' page
5

Given A participant "William Mcmahon" logged in to FastTrack application 10s 97ms

And user navigates to 'Calendar' -> 'Filter' tab and clicks 'Metro' tab 6s 283ms

When user views the 'Calendar' page and filters by 'Metro' option 2s 16ms

Then User verifies the details with filter 'Metro' 0s

After 421ms Screenshot +

@test
Scenario:Verify that user can view the 'PFS' details on 'Calendar' page
5

Given A participant "William Mcmahon" logged in to FastTrack application 10s 91ms

And user navigates to 'Calendar' -> 'Filter' tab and clicks 'PFS' tab 6s 339ms

When user views the 'Calendar' page and filters by 'PFS' option 2s 78ms

Then User verifies the details with filter 'PFS' 0s

After 427ms Screenshot +

@test
Scenario:Verify that user can view the 'Tier 3' details on 'Calendar' page
5

Given A participant "William Mcmahon" logged in to FastTrack application 10s 105ms

And user navigates to 'Calendar' -> 'Filter' tab and clicks 'Tier 3' tab 6s 293ms

When user views the 'Calendar' page and filters by 'Tier 3' option 2s 12ms

Then User verifies the details with filter 'Tier 3' 0s

After 472ms Screenshot +

@test
Scenario:Verify that user can view the 'RLM' details on 'Calendar' page
5

Given A participant "William Mcmahon" logged in to FastTrack application 10s 179ms

And user navigates to 'Calendar' -> 'Filter' tab and clicks 'Metro' tab 6s 283ms

When user views the 'Calendar' page and filters by 'RLM' option 1s 989ms

Then User verifies the details with filter 'RLM' 0s

After 411ms Screenshot +

@test
Scenario:Verify that user can view the 'HSM' details on 'Calendar' page
5

Given A participant "William Mcmahon" logged in to FastTrack application 10s 391ms

And user navigates to 'Calendar' -> 'Filter' tab and clicks 'Metro' tab 6s 275ms

When user views the 'Calendar' page and filters by 'HSM' option 2s 57ms

Then User verifies the details with filter 'HSM' 0s

After 418ms Screenshot +

@test
Scenario:Verify that user can view the 'CS' details on 'Calendar' page
5

Given A participant "William Mcmahon" logged in to FastTrack application 10s 395ms

And user navigates to 'Calendar' -> 'Filter' tab and clicks 'CS' tab 6s 294ms

When user views the 'Calendar' page and filters by 'CS' option 2s 975ms

Then User verifies the details with filter 'CS' 0s

After 417ms Screenshot +

Feature:Participants login credentials to the FT1.9 1

@test
Scenario:Verify if the participant can login with correct memberid and password
4

Given A participant logs in with 'correct memberid' and 'correct password' 6s 213ms

When user clicks 'continue' button to login 2s 896ms

Then user should be able to land on Home page 22s 11ms

After 458ms Screenshot +

Feature:Login to the FT1.9 application and verify the overlays 1

@test
Scenario:Verify Overlay at 'I Want To' Page
4

Given A participant "William Mcmahon" logged in to FastTrack application 10s 421ms

When user views the overlay at 'I Want To' Page and clicks at 'Got it' 1s 509ms

Then user is able to land on 'I Want To' Page 0s

After 398ms Screenshot +

Feature:FT2-679 Owner can view a syndicate 1 1

@test
Scenario:QA-241 Verify if a user can view a Syndicate
6

Given A participant "William Mcmahon" logged in to FastTrack application 10s 757ms

And user navigates to 'Account' -> 'Syndicates' tab and clicks 'View Details' tab 13s 268ms

When user navigates view details link of a syndicate 4ms

Then User should be navigated to the syndicate details page 8s 44ms

And User should be able to view the financial details, members and greyhounds that belong to the Syndicate 1ms

After 652ms Screenshot +

@test
Scenario:FT2-545 As a manager I want to add new manager for syndicate members
3 3 1

Given A participant "David Long" logged in to FastTrack application 10s 617ms

And user navigates to 'Account' -> 'Syndicates' tab and clicks 'View Details' tab 12s 347ms

When user clicks 'Manage Syndicate' 9s 83ms Show Error + 
                                            
 WebDriverError: element click intercepted: Element (span class="mat-button-wrapper")...(/span) is not clickable at point (186, 63). Other element would receive the click: (div _ngcontent-wee-c86="" class="test-release-title")...(/div)
  (Session info: chrome=86.0.4240.198)
  (Driver info: chromedriver=85.0.4183.38 (9047dbc2c693f044042bbec5c91401c708c7c26a-refs/branch-heads/4183@{#779}),platform=Windows NT 10.0.18363 x86_64)
    at Object.checkLegacyResponse (C:\Users\psingh\Desktop\Priti\Automation1.9\TestAutomationFramework-FT1.9\node_modules\selenium-webdriver\lib\error.js:546:15)
    at parseHttpResponse (C:\Users\psingh\Desktop\Priti\Automation1.9\TestAutomationFramework-FT1.9\node_modules\selenium-webdriver\lib\http.js:509:13)
    at C:\Users\psingh\Desktop\Priti\Automation1.9\TestAutomationFramework-FT1.9\node_modules\selenium-webdriver\lib\http.js:441:30
    at runMicrotasks ((anonymous))
    at processTicksAndRejections (internal/process/task_queues.js:97:5)
From: Task: WebElement.click()
    at Driver.schedule (C:\Users\psingh\Desktop\Priti\Automation1.9\TestAutomationFramework-FT1.9\node_modules\selenium-webdriver\lib\webdriver.js:807:17)
    at WebElement.schedule_ (C:\Users\psingh\Desktop\Priti\Automation1.9\TestAutomationFramework-FT1.9\node_modules\selenium-webdriver\lib\webdriver.js:2010:25)
    at WebElement.click (C:\Users\psingh\Desktop\Priti\Automation1.9\TestAutomationFramework-FT1.9\node_modules\selenium-webdriver\lib\webdriver.js:2092:17)
    at actionFn (C:\Users\psingh\Desktop\Priti\Automation1.9\TestAutomationFramework-FT1.9\node_modules\protractor\built\element.js:89:44)
    at Array.map ((anonymous))
    at C:\Users\psingh\Desktop\Priti\Automation1.9\TestAutomationFramework-FT1.9\node_modules\protractor\built\element.js:461:65
    at ManagedPromise.invokeCallback_ (C:\Users\psingh\Desktop\Priti\Automation1.9\TestAutomationFramework-FT1.9\node_modules\selenium-webdriver\lib\promise.js:1376:14)
    at TaskQueue.execute_ (C:\Users\psingh\Desktop\Priti\Automation1.9\TestAutomationFramework-FT1.9\node_modules\selenium-webdriver\lib\promise.js:3084:14)
    at TaskQueue.executeNext_ (C:\Users\psingh\Desktop\Priti\Automation1.9\TestAutomationFramework-FT1.9\node_modules\selenium-webdriver\lib\promise.js:3067:27)
    at C:\Users\psingh\Desktop\Priti\Automation1.9\TestAutomationFramework-FT1.9\node_modules\selenium-webdriver\lib\promise.js:2927:27
    at C:\Users\psingh\Desktop\Priti\Automation1.9\TestAutomationFramework-FT1.9\node_modules\selenium-webdriver\lib\promise.js:668:7
    at runMicrotasks ((anonymous))
    at processTicksAndRejections (internal/process/task_queues.js:97:5)Error
    at ElementArrayFinder.applyAction_ (C:\Users\psingh\Desktop\Priti\Automation1.9\TestAutomationFramework-FT1.9\node_modules\protractor\built\element.js:459:27)
    at ElementArrayFinder.(computed) [as click] (C:\Users\psingh\Desktop\Priti\Automation1.9\TestAutomationFramework-FT1.9\node_modules\protractor\built\element.js:91:29)
    at ElementFinder.(computed) [as click] (C:\Users\psingh\Desktop\Priti\Automation1.9\TestAutomationFramework-FT1.9\node_modules\protractor\built\element.js:831:22)
    at C:\Users\psingh\Desktop\Priti\Automation1.9\TestAutomationFramework-FT1.9\stepdefinitions\When.ts:356:35
    at Generator.next ((anonymous))
    at fulfilled (C:\Users\psingh\Desktop\Priti\Automation1.9\TestAutomationFramework-FT1.9\JSFiles\stepDefinitions\When.js:5:58)
    at runMicrotasks ((anonymous))
    at processTicksAndRejections (internal/process/task_queues.js:97:5)

And user adds a new member using FT member no. and clicks Add member button 0s

And User clicks on 'submit' button 0s

Then user should be able to see the added member with Incomplete status 0s

After 416ms Screenshot +

generated by @cucumber-html-reporter